Can one of the admins verify this patch?

Hi @josedonizetti. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: josedonizetti
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: balopat

If they are not already assigned, you can assign the PR to them by writing /assign @balopat in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

@minikube-bot OK test

@josedonizetti thank for your contributions, would you please add documentation and integration tests for it ? and how one would use this --version ?

@medyagh The usage will be docker-machine-driver-kvm2 --version. The idea is to simplify issues communication about the kvm2 driver, the user would have a simple way to know the driver is outdated, and probably the reason it's currently failing. I'll add the documentation and tests. Thanks

@medyagh @josedonizetti I think it should be --kvm-version instead of just --version. That way, people don't get confused if that is the minikube's version or the kvm driver version. What do you think?

@blueelvis I think the command docker-machine-driver-kvm2 --version is very explanatory that is not the same as minikube --version. Yet, no strong feelings about it, let's see what others think. :)

@medyagh Hey, have any pointers on adding integration tests for this?